View M50FLW080AK5T_1350779.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

1/53 june 2005 m50flw080a m50flw080b 8 mbit (13 x 64kbyte blocks + 3 x 16 x 4kbyte sectors) 3v supply firmware hub / low pin count flash memory features summary flash memory ? compatible with either the lpc interface or the fwh interface (intel spec rev1.1) used in pc bios applications ? 5 signal communication interface supporting read and write operations ? 5 additional general purpose inputs for platform design flexibility ? synchronized with 33mhz pci clock 16 blocks of 64 kbytes ? 13 blocks of 64 kbytes each ? 3 blocks, subdivided into 16 uniform sectors of 4 kbytes each two blocks at the top and one at the bottom (m50flw080a) one block at the top and two at the bottom (m50flw080b) enhanced security ? hardware write protect pins for block protection ? register-based read and write protection ? individual lock register for each 4 kbyte sector supply voltage ?v cc = 3.0 to 3.6v for program, erase and read operations ?v pp = 12v for fast program and erase two interfaces ? auto detection of firmware hub (fwh) or low pin count (lpc) memory cycles for embedded operation with pc chipsets ? address/address multiplexed (a/a mux) interface for programming equipment compatibility. programming time: 10s typical program/erase controller ? embedded program and erase algorithms ? status register bits figure 1. packages program/erase suspend ? read other blocks/sectors during program suspend ? program other blocks/sectors during erase suspend electronic signature ? manufacturer code: 20h ? device code (m50flw080a): 80h ? device code (m50flw080b): 81h tsop32 (nb) 8 x 14mm plcc32 (k) tsop40 (n) 10 x 20mm
m50flw080a, m50flw080b 2/53 table of contents features summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 figure 1. packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 summary description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 figure 2. logic diagram (fwh/lpc interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 figure 3. logic diagram (a/a mux interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 table 1. signal names (fwh/lpc interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 table 2. signal names (a/a mux interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 figure 4. plcc connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 figure 5. tsop32 connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 figure 6. tsop40 connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 table 3. addresses (m50flw080a) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 table 4. addresses (m50flw080b) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 firmware hub/low pin count (fwh/lpc) signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . 10 input/output communications (fwh0/lad0-fwh3/lad3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 input communication frame (fwh4/lframe). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 identification inputs (id0-id3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 general purpose inputs (gpi0-gpi4).. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 interface configuration (ic). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 interface reset (rp ). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 cpu reset (init ). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 clock (clk). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 top block lock (tbl ). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 write protect (wp ). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 reserved for future use (rfu). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 address/address multiplexed (a/a mux) signal description s . . . . . . . . . . . . . . . . . . . . . . . . . 11 address inputs (a0-a10). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 data inputs/outputs (dq0-dq7). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 output enable (g ). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 write enable (w ). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 row/column address select (rc ). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 supply signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 v cc supply voltage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 v pp optional supply voltage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 v ss ground. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 table 5. memory identification input configuration (lpc mode). . . . . . . . . . . . . . . . . . . . . . . . . . 12 bus operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 firmware hub/low pin count (fwh/lpc) bus operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 bus read. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 bus write. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3/53 m50flw080a, m50flw080b bus abort. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 standby. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 block protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 address/address multiplexed (a/a mux) bus operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 bus read. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 bus write. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 output disable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 table 6. fwh bus read field definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 figure 7. fwh bus read waveforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 table 7. fwh bus write field definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 figure 8. fwh bus write waveforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 table 8. lpc bus read field definitions (1-byte). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 figure 9. lpc bus read waveforms (1-byte) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 table 9. lpc bus write field definitions (1 byte) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 figure 10.lpc bus write waveforms (1 byte) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 table 10. a/a mux bus operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 command interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 table 11. command codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 read memory array command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 read status register command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 read electronic signature command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 8 table 12. electronic signature codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 program command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 quadruple byte program command (a/a mux interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 double/quadruple byte program command (fwh mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 chip erase command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 block erase command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 sector erase command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 clear status register command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 program/erase suspend command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 program/erase resume command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 table 13. commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 status register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 program/erase controller status (bit sr7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2 erase suspend status (bit sr6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 erase status (bit sr5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 program status (bit sr4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 v pp status (bit sr3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 program suspend status (bit sr2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 block/sector protection status (bit sr1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 reserved (bit sr0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 table 14. status register bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
m50flw080a, m50flw080b 4/53 firmware hub/low pin count (fwh/lpc) in terface configuration registers . . . 24 lock registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 write lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 read lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 lock down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 table 15. configuration register map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 table 16. lock register bit definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 table 17. general purpose inputs register definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 firmware hub/low pin count (fwh/lpc) general purpose input register . . . . . . . . . . . . . . 25 manufacturer code register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 program and erase times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 table 18. program and erase times. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 maximum rating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 table 19. absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 7 dc and ac parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 table 20. operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 table 21. fwh/lpc interface ac measurement conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 table 22. a/a mux interface ac measurement conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 figure 11.fwh/lpc interface ac measurement i/o waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . 28 figure 12.a/a mux interface ac measurement i/o waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 figure 13.ac measurement load circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 table 23. impedance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 table 24. dc characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 figure 14.fwh/lpc interface clock waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 table 25. fwh/lpc interface clock characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 figure 15.fwh/lpc interface ac signal timing waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 table 26. fwh/lpc interface ac signal timing characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . 32 figure 16.reset ac waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 table 27. reset ac characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 figure 17.a/a mux interface read ac waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 table 28. a/a mux interface read ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 figure 18.a/a mux interface write ac waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 table 29. a/a mux interface write ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 package mechanical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 figure 19.plcc32 ? 32 pin rectangular plastic leaded chip carrier, package outline . . . . . . . . 36 table 30. plcc32 ? 32 pin rectangular plastic leaded chip carrier, package mechanical data 37 figure 20.tsop32 ? 32 lead plastic thin small outline, 8x14 mm, package outline . . . . . . . . . . 38 table 31. tsop32 ? 32 lead plastic thin small outline, 8x14 mm, package mechanical data. . . 38 figure 21.tsop40 ? 40 lead plastic thin small outline, 10 x 20mm, package outline. . . . . . . . . 39 table 32. tsop40 ? 40 lead plastic thin small outline, 10 x 20mm, package mechanical data . 39
5/53 m50flw080a, m50flw080b part numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 table 33. ordering information scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 0 appendix a.block and sector address table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 table 34. m50flw080a block, sector and lock register addresses . . . . . . . . . . . . . . . . . . . . . . 41 table 35. m50flw080b block, sector and lock register addresses . . . . . . . . . . . . . . . . . . . . . . 43 appendix b.flowcharts and pseudo codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 figure 22.program flowchart and pseudo code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 figure 23.double/quadruple byte program flowchart and pseudo code (fwh mode only). . . . . 46 figure 24.quadruple byte program flowchart and pseudo code (a/a mux interface only) . . . . . 47 figure 25.program suspend and resume flowchart and pseudo code . . . . . . . . . . . . . . . . . . . . 48 figure 26.chip erase flowchart and pseudo code (a/a mux interface only) . . . . . . . . . . . . . . . . 49 figure 27.sector/block erase flowchart and pseudo code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 figure 28.erase suspend and resume flowchart and pseudo code . . . . . . . . . . . . . . . . . . . . . . 51 revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 table 36. document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
m50flw080a, m50flw080b 6/53 summary description the m50flw080 is a 8 mbit (1m x8) non-volatile memory that can be read, erased and repro- grammed. these operations can be performed us- ing a single low voltage (3.0 to 3.6v) supply. for fast programming and fast erasing on production lines, an optional 12v power supply can be used to reduce the erasing and programming time. the memory is divided into 16 uniform blocks of 64 kbytes each, three of which are divided into 16 uniform sectors of 4 kbytes each (see appendix a. for details). all blocks and sectors can be erased independently. so, it is possible to pre- serve valid data while old data is erased. blocks can be protected individually to prevent accidental program or erase commands from modifying their contents. program and erase commands are written to the command interface of the memory. an on-chip program/erase controller simplifies the process of programming or erasing the memory by taking care of all of the special operations that are re- quired to update the memory contents. the end of a program or erase operation can be detected and any error conditions identified. the command set to control the memory is consistent with the je- dec standards. two different bus interfaces are supported by the memory: the primary interface, the fwh/lpc interface, uses intel?s proprietary firmware hub (fwh) and low pin count (lpc) protocol. this has been designed to remove the need for the isa bus in current pc chipsets. the m50flw080 acts as the pc bios on the low pin count bus for these pc chipsets. the secondary interface, the address/ address multiplexed (or a/a mux) interface, is designed to be compatible with current flash programmers, for production line programming prior to fitting the device in a pc motherboard. the memory is supplied with all the bits erased (set to ?1?).
7/53 m50flw080a, m50flw080b figure 2. logic diagram (fwh/lpc interface) figure 3. logic diagram (a/a mux interface) table 1. signal names (fwh/lpc interface) table 2. signal names (a/a mux interface) ai09229b 4 fwh4/lframe fwh0/lad0 fwh3/lad3 v cc m50flw080a m50flw080b clk v ss 4 ic rp tbl 5 init wp id0-id3 gpi0- gpi4 v pp ai09230b 11 rc dq0-dq7 v cc m50flw080a m50flw080b ic v ss 8 g w rp a0-a10 v pp fwh0/lad0- fwh3/lad3 input/output communications fwh4/ lframe input communication frame id0-id3 identification inputs (id0 and id1 are reserved for future use (rfu) in lpc mode) gpi0-gpi4 general purpose inputs ic interface configuration rp interface reset init cpu reset clk clock tbl top block lock wp write protect rfu reserved for future use. leave disconnected v cc supply voltage v pp optional supply voltage for fast program and erase operations v ss ground nc not connected internally ic interface configuration a0-a10 address inputs dq0-dq7 data inputs/outputs g output enable w write enable rc row/column address select rp interface reset v cc supply voltage v pp optional supply voltage for fast program and erase operations v ss ground nc not connected internally
m50flw080a, m50flw080b 8/53 figure 4. plcc connections note: pins 27 and 28 are not internally connected. figure 5. tsop32 connections ai09231c gpi4 nc fwh4/lframe rfu 17 id1/rfu id0/rfu fwh0/lad0 fwh1/lad1 fwh2/lad2 fwh3/lad3 rfu gpi1 tbl id3 id2 gpi0 wp 9 clk v ss 1 rp v cc nc gpi2 rfu 32 v pp v cc m50flw080a m50flw080b gpi3 ic (v il ) rfu init nc 25 v ss a1 a0 dq0 a7 a4 a3 a2 a6 a5 a10 rc rp a8 v pp v cc a9 nc w v ss v cc nc dq7 ic (v ih ) g nc dq5 dq1 dq2 dq3 dq4 dq6 v ss a/a mux a/a mux a/a mux a/a mux ai09701b a1 a0 dq0 a7 a4 a3 a2 a6 a5 a9 a8 w dq7 g nc dq5 dq1 dq2 dq3 dq4 dq6 a/a mux a/a mux id1/rfu fwh1/lad1 fwh2/lad2 gpi3 tbl id2 gpi0 wp nc nc rfu gpi4 nc fwh4/lframe rfu fwh3/lad3 v ss rfu rfu clk rp v pp v cc m50flw080a m50flw080b 8 1 9 16 17 24 25 32 id3 v ss init ic nc gpi2 fwh0/lad0 gpi1 id0/rfu nc nc ic (v ih ) nc nc rc rp v pp v cc a10 v ss
9/53 m50flw080a, m50flw080b figure 6. tsop40 connections table 3. addresses (m50flw080a) table 4. addresses (m50flw080b) note: also see appendix a. , table 34. and table 35. for a full listing of the block addresses. ai09232c a1 a0 dq0 a7 a4 a3 a2 a6 a5 a9 a8 w v ss v cc dq7 g nc dq5 dq1 dq2 dq3 dq4 dq6 a/a mux a/a mux id1/rfu fwh1/lad1 fwh2/lad2 gpi3 tbl id2 gpi0 wp nc v cc nc ic (v il ) rfu gpi4 nc v ss fwh4/lframe rfu fwh3/lad3 v ss v cc rfu rfu nc clk rp nc v pp v cc nc m50flw080a m50flw080b 10 1 11 20 21 30 31 40 id3 nc init nc nc gpi2 fwh0/lad0 gpi1 id0/rfu v ss nc nc nc ic (v ih ) nc nc nc nc rc rp v pp v cc nc a10 v ss v ss v cc block size (kbyte) address range sector size (kbyte) 64 f0000h-fffffh 16 x 4 kbytes 64 e0000h-effffh 16 x 4 kbytes 64 d0000h-dffffh 13 x 64 kbytes 64 c0000h-cffffh 64 b0000h-bffffh 64 a0000h-affffh 64 90000h-9ffffh 64 80000h-8ffffh 64 70000h-7ffffh 64 60000h-6ffffh 64 50000h-5ffffh 64 40000h-4ffffh 64 30000h-3ffffh 64 20000h-2ffffh 64 10000h-1ffffh 64 00000h-0ffffh 16 x 4 kbytes block size (kbyte) address range sector size (kbyte) 64 f0000h-fffffh 16 x 4 kbytes 64 e0000h-effffh 13 x 64 kbytes 64 d0000h-dffffh 64 c0000h-cffffh 64 b0000h-bffffh 64 a0000h-affffh 64 90000h-9ffffh 64 80000h-8ffffh 64 70000h-7ffffh 64 60000h- 6ffffh 64 50000h- 5ffffh 64 40000h- 4ffffh 64 30000h-3ffffh 64 20000h-2ffffh 64 10000h-1ffffh 16 x 4 kbytes 64 00000h-0ffffh 16 x 4 kbytes
m50flw080a, m50flw080b 10/53 signal descriptions there are two distinct bus interfaces available on this device. the active interface is selected before power-up, or during reset, using the interface configuration pin, ic. the signals for each interface are discussed in the firmware hub/low pin count (fwh/lpc) signal descriptions section and the address/address multiplexed (a/a mux) signal descriptions sec- tion, respectively, while the supply signals are dis- cussed in the supply signal descriptions section. firmware hub/low pin count (fwh/lpc) signal descriptions please see figure 2. and table 1. . input/output communications (fwh0/lad0- fwh3/lad3). all input and output communica- tions with the memory take place on these pins. addresses and data for bus read and bus write operations are encoded on these pins. input communication frame (fwh4/ lframe ). the input communication frame (fwh4/lframe ) signal indicates the start of a bus operation. when input communication frame is low, v il , on the rising edge of the clock, a new bus operation is initiated. if input communication frame is low, v il , during a bus operation then the operation is aborted. when input communication frame is high, v ih , the current bus operation is ei- ther proceeding or the bus is idle. identification inputs (id0-id3). up to 16 memo- ries can be addressed on a bus, in the firmware hub (fwh) mode. the identification inputs allow each device to be given a unique 4-bit address. a ?0? is signified on a pin by driving it low, v il , or leaving it floating (since there is an internal pull- down resistor, with a value of r il ). a ?1? is signified on a pin by driving it high, v ih (and there will be a leakage current of i li2 through the pin). by convention, the boot memory must have ad- dress ?0000?, and all additional memories are giv- en addresses, allocated sequentially, from ?0001?. in the low pin count (lpc) mode, the identifica- tion inputs (id2-id3) can address up to 4 memo- ries on a bus. in the lpc mode, the id0 and id1 signals are reserved for future use (rfu). the value on address a20-a21 is compared to the hardware strapping on the id2-id3 lines to select the memory that is being addressed. for an ad- dress bit to be ?1?, the corresponding id pin can be left floating or driven low, v il (again, with the in- ternal pull-down resistor, with a value of r il ). for an address bit to be ?0?, the corresponding id pin must be driven high, v ih (and there will be a leak- age current of i li2 through the pin, as specified in table 24. ). for details, see table 5. . general purpose inputs (gpi0-gpi4). the general purpose inputs can be used as digital in- puts for the cpu to read, with their contents being available in the general purpose inputs register. the pins must have stable data throughout the en- tire cycle that reads the general purpose input register. these pins should be driven low, v il, or high, v ih , and must not be left floating. interface configuration (ic). the interface con- figuration input selects whether the fwh/lpc in- terface or the address/address multiplexed (a/a mux) interface is used. the state of the interface configuration, ic, should not be changed during operation of the memory device, except for select- ing the desired interface in the period before pow- er-up or during a reset. to select the fwh/lpc interface, the interface configuration pin should be left to float or driven low, v il . to select the address/address multi- plexed (a/a mux) interface, the pin should be driv- en high, v ih . an internal pull-down resistor is included with a value of r il ; there will be a leakage current of i li2 through each pin when pulled to v ih . interface reset (rp ). the interface reset (rp ) input is used to reset the device. when interface reset (rp ) is driven low, v il , the memory is in reset mode (the outputs go to high impedance, and the current consumption is minimized). when rp is driven high, v ih , the device is in normal op- eration. after exiting reset mode, the memory en- ters read mode. cpu reset (init ). the cpu reset, init , signal is used to reset the device when the cpu is reset. it behaves identically to interface reset, rp , and the internal reset line is the logical or (electrical and) of rp and init . clock (clk). the clock, clk, input is used to clock the signals in and out of the input/output communication pins, fwh0/lad0-fwh3/lad3. the clock conforms to the pci specification. top block lock (tbl ). the top block lock in- put is used to prevent the top block (block 15) from being changed. when top block lock, tbl , is driven low, v il , program and erase operations in the top block have no effect, regardless of the state of the lock register. when top block lock, tbl , is driven high, v ih , the protection of the block is determined by the lock registers. the state of top block lock, tbl , does not affect the protec- tion of the main blocks (blocks 0 to 14). for de- tails, see appendix a. . top block lock, tbl , must be set prior to a pro- gram or erase operation being initiated, and must not be changed until the operation has completed, otherwise unpredictable results may occur. simi- larly, unpredictable behavior is possible if wp is
11/53 m50flw080a, m50flw080b changed during program or erase suspend, and care should be taken to avoid this. write protect (wp ). the write protect input is used to prevent the main blocks (blocks 0 to 14) from being changed. when write protect, wp , is driven low, v il , program and erase operations in the main blocks have no effect, regardless of the state of the lock register. when write protect, wp , is driven high, v ih , the protection of the block or sector is determined by the lock registers. the state of write protect, wp , does not affect the pro- tection of the top block (block 15). for details, see appendix a. . write protect, wp , must be set prior to a program or erase operation is initiated, and must not be changed until the operation has completed other- wise unpredictable results may occur. similarly, unpredictable behavior is possible if wp is changed during program or erase suspend, and care should be taken to avoid this. reserved for future use (rfu). reserved for future use (rfu). these pins do not presently have assigned functions. they must be left discon- nected, except for id0 and id1 (when in lpc mode) which can be left connected. the electrical characteristics for these signals are as described in the ? identification inputs (id0-id3). ? section. address/address multiplexed (a/a mux) signal descriptions please see figure 3. and table 2. . address inputs (a0-a10). the address inputs are used to set the row address bits (a0-a10) and the column address bits (a11-a19). they are latched during any bus operation by the row/col- umn address select input, rc . data inputs/outputs (dq0-dq7). the data in- puts/outputs hold the data that is to be written to or read from the memory. they output the data stored at the selected address during a bus read operation. during bus write operations they carry the commands that are sent to the command in- terface of the internal state machine. the data in- puts/outputs, dq0-dq7, are latched during a bus write operation. output enable (g ). the output enable signal, g , controls the output buffers during a bus read op- eration. write enable (w ). the write enable signal, w , controls the bus write operation of the command interface. row/column address select (rc ). the row/ column address select input selects whether the address inputs are to be latched into the row ad- dress bits (a0-a10) or the column address bits (a11-a19). the row address bits are latched on the falling edge of rc whereas the column ad- dress bits are latched on its rising edge. supply signal descriptions the supply signals are the same for both interfac- es. v cc supply voltage. the v cc supply voltage supplies the power for all operations (read, pro- gram, erase, etc.). the command interface is disabled when the v cc supply voltage is less than the lockout voltage, v lko . this is to prevent bus write operations from accidentally damaging the data during power up, power down and power surges. if the program/ erase controller is programming or erasing during this time, the operation aborts, and the memory contents that were being altered will be invalid. af- ter v cc becomes valid, the command interface is reset to read mode. a 0.1f capacitor should be connected between the v cc supply voltage pins and the v ss ground pin to decouple the current surges from the power supply. both v cc supply voltage pins must be connected to the power supply. the pcb track widths must be sufficient to carry the currents re- quired during program and erase operations. v pp optional supply voltage. the v pp optional supply voltage pin is used to select the fast pro- gram (see the quadruple byte program command description in a/a mux interface and the double/ quadruple byte program command description in fwh mode) and fast erase options of the memo- ry. when v pp = v cc , program and erase operations take place as normal. when v pp = v pph , fast pro- gram and erase operations are used. any other voltage input to v pp will result in undefined behav- ior, and should not be used. v pp should not be set to v pph for more than 80 hours during the life of the memory. v ss ground. v ss is the reference for all the volt- age measurements.
m50flw080a, m50flw080b 12/53 table 5. memory identification input configuration (lpc mode) bus operations the two interfaces, a/a mux and fwh/lpc, sup- port similar operations, but with different bus sig- nals and timings. the firmware hub/low pin count (fwh/lpc) interface offers full functional- ity, while the address/address multiplexed (a/a mux) interface is orientated for erase and program operations. see the sections below, the firmware hub/low pin count (fwh/lpc) bus operations and ad- dress/address multiplexed (a/a mux) bus opera- tions , for details of the bus operations on each interface. firmware hub/low pin count (fwh/lpc) bus operations the m50flw080 automatically identifies the type of fwh/lpc protocol from the first received nibble (start nibble) and decodes the data that it re- ceives afterwards, according to the chosen fwh or lpc mode. the firmware hub/low pin count (fwh/lpc) interface consists of four data signals (fwh0/lad0-fwh3/lad3), one control line (fwh4/lframe ) and a clock (clk). protection against accidental or malicious data corruption is achieved using two additional signals (tbl and wp ). and two reset signals (rp and init ) are available to put the memory into a known state. the data, control and clock signals are designed to be compatible with pci electrical specifications. the interface operates with clock speeds of up to 33mhz. the following operations can be performed using the appropriate bus cycles: bus read, bus write, standby, reset and block protection. bus read. bus read operations are used to read from the memory cells, specific registers in the command interface or firmware hub/low pin count registers. a valid bus read operation starts on the rising edge of the clock signal when the input communication frame, fwh4/ lframe , is low, v il , and the correct start cycle is present on fwh0/lad0-fwh3/lad3. on sub- sequent clock cycles the host will send to the memory: id select, address and other control bits on fwh0-fwh3 in fwh mode. type+dir address and other control bits on lad0-lad3 in lpc mode. the device responds by outputting sync data until the wait states have elapsed, followed by data0- data3 and data4-data7. see table 6. and table 8. , and figure 7. and fig- ure 9. , for a description of the field definitions for each clock cycle of the transfer. see table 26. , and figure 15. , for details on the timings of the sig- nals. bus write. bus write operations are used to write to the command interface or firmware hub/low pin count registers. a valid bus write operation starts on the rising edge of the clock signal when input communication frame, fwh4/lframe , is low, v il , and the correct start cycle is present on fwh0/lad0-fwh3/lad3. on subsequent clock cycles the host will send to the memory: id select, address, other control bits, data0- data3 and data4-data7 on fwh0-fwh3 in fwh mode. cycle type + dir, address, other control bits, data0-data3 and data4-data7 on lad0- lad3. the device responds by outputting sync data until the wait states have elapsed. see table 7. and table 9. , and figure 8. and fig- ure 10. , for a description of the field definitions for each clock cycle of the transfer. see table 26. , and figure 15. , for details on the timings of the sig- nals. bus abort. the bus abort operation can be used to abort the current bus operation immediately. a bus abort occurs when fwh4/lframe is driven low, v il , during the bus operation. the device puts the input/output communication pins, fwh0/lad0-fwh3/lad3, to high impedance. memory number id3 id2 a21 a20 1 (boot memory) v il or float v il or float 11 2 v il or float v ih 10 3 v ih v il or float 01 4 v ih v ih 00
13/53 m50flw080a, m50flw080b note that, during a bus write operation, the com- mand interface starts executing the command as soon as the data is fully received. a bus abort dur- ing the final tar cycles is not guaranteed to abort the command. the bus, however, will be released immediately. standby. when fwh4/lframe is high, v ih , the device is put into standby mode, where fwh0/ lad0-fwh3/lad3 are put into a high-impedance state and the supply current is reduced to the standby level, i cc1 . reset. during the reset mode, all internal circuits are switched off, the device is deselected, and the outputs are put to high-impedance. the device is in the reset mode when interface reset, rp , or cpu reset, init , is driven low, v il . rp or init must be held low, v il , for t plph . the memory re- verts to the read mode upon return from the re- set mode, and the lock registers return to their default states regardless of their states before re- set. if rp or init goes low, v il , during a program or erase operation, the operation is aborted and the affected memory cells no longer contain valid data. the device can take up to t plrh to abort a program or erase operation. block protection. block protection can be forced using the signals top block lock, tbl , and write protect, wp , regardless of the state of the lock registers. address/address multiplexed (a/a mux) bus operations the address/address multiplexed (a/a mux) inter- face has a more traditional-style interface. the sig- nals consist of a multiplexed address signals (a0- a10), data signals, (dq0-dq7) and three control signals (rc , g , w ). an additional signal, rp , can be used to reset the memory. the address/address multiplexed (a/a mux) inter- face is included for use by flash programming equipment for faster factory programming. only a subset of the features available to the firmware hub (fwh)/low pin count (lpc) interface are available; these include all the commands but ex- clude the security features and other registers. the following operations can be performed using the appropriate bus cycles: bus read, bus write, output disable and reset. when the address/address multiplexed (a/a mux) interface is selected, all the blocks are unprotect- ed. it is not possible to protect any blocks through this interface. bus read. bus read operations are used to read the contents of the memory array, the electronic signature or the status register. a valid bus read operation begins by latching the row address and column address signals into the memory using the address inputs, a0-a10, and the row/column address select rc . write enable (w ) and inter- face reset (rp ) must be high, v ih , and output enable, g , low, v il . the data inputs/outputs will output the value, according to the timing con- straints specified in figure 17. , and table 28. . bus write. bus write operations are used to write to the command interface. a valid bus write oper- ation begins by latching the row address and col- umn address signals into the memory using the address inputs, a0-a10, and the row/column ad- dress select rc . the data should be set up on the data inputs/outputs; output enable, g , and inter- face reset, rp , must be high, v ih ; and write en- able, w , must be low, v il . the data inputs/ outputs are latched on the rising edge of write en- able, w . see figure 18. , and table 29. , for details of the timing requirements. output disable. the data outputs are high-im- pedance when the output enable, g , is at v ih . reset. during the reset mode, all internal circuits are switched off, the device is deselected, and the outputs are put at high-impedance. the device is in the reset mode when rp is low, v il . rp must be held low, v il for t plph . if rp goes low, v il , during a program or erase operation, the opera- tion is aborted, and the affected memory cells no longer contain valid data. the memory can take up to t plrh to abort a program or erase operation.
m50flw080a, m50flw080b 14/53 table 6. fwh bus read field definitions figure 7. fwh bus read waveforms clock cycle number clock cycle count field fwh0- fwh3 memory i/o description 1 1 start 1101b i on the rising edge of clk with fwh4 low, the contents of fwh0- fwh3 indicate the start of a fwh read cycle. 21idselxxxxi indicates which fwh flash memory is selected. the value on fwh0-fwh3 is compared to the idsel strapping on the fwh flash memory pins to select which fwh flash memory is being addressed. 3-9 7 addr xxxx i a 28-bit address is transferred, with the most significant nibble first. for the multi-byte read operation, the least significant bits (msize of them) are treated as don't care, and the read operation is started with each of these bits reset to 0. address lines a20-21 and a23-27 are treated as don?t care during a normal memory array access, with a22=1, but are taken into account for a register access, with a22=0. (see table 15. ) 10 1 msize xxxx i this one clock cycle is driven by the host to determine the number of bytes that will be transferred. m50flw080 supports: single byte transfer (0000b), 2-byte transfer (0001b), 4-byte transfer (0010b), 16-byte transfer (0100b) and 128-byte transfer (0111b). 11 1 tar 1111b i the host drives fwh0-fwh3 to 1111b to indicate a turnaround cycle. 12 1 tar 1111b (float) o the fwh flash memory takes control of fwh0-fwh3 during this cycle. 13-14 2 wsync 0101b o the fwh flash memory drives fwh0-fwh3 to 0101b (short wait-sync) for two clock cycles, indicating that the data is not yet available. two wait-states are always included. 15 1 rsync 0000b o the fwh flash memory drives fwh0-fwh3 to 0000b, indicating that data will be available during the next clock cycle. 16-17m=2ndataxxxx o data transfer is two clk cycles, starting with the least significant nibble. if multi-byte read operation is enabled, repeat cycle-16 and cycle-17 n times, where n = 2 msize . previous +1 1 tar 1111b o the fwh flash memory drives fwh0-fwh3 to 1111b to indicate a turnaround cycle. previous +1 1tar 1111b (float) n/a the fwh flash memory floats its outputs, the host takes control of fwh0-fwh3. ai08433b clk fwh4 fwh0-fwh3 number of clock cycles start idsel addr msize tar sync data tar 117123m2
15/53 m50flw080a, m50flw080b table 7. fwh bus write field definitions figure 8. fwh bus write waveforms clock cycle number clock cycle count field fwh0- fwh3 memory i/o description 1 1 start 1110b i on the rising edge of clk with fwh4 low, the contents of fwh0-fwh3 indicate the start of a fwh write cycle. 21idselxxxxi indicates which fwh flash memory is selected. the value on fwh0-fwh3 is compared to the idsel strapping on the fwh flash memory pins to select which fwh flash memory is being addressed. 3-9 7 addr xxxx i a 28-bit address is transferred, with the most significant nibble first. address lines a20-21 and a23-27 are treated as don?t care during a normal memory array access, with a22=1, but are taken into account for a register access, with a22=0. (see table 15. ) 10 1 msize xxxx i 0000(single byte transfer) 0001 (double byte transfer) 0010b (quadruple byte transfer). 11-18 m=2/4/8 data xxxx i data transfer is two cycles, starting with the least significant nibble. (the first pair of nibbles is that at the address with a1- a0 set to 00, the second pair with a1-a0 set to 01, the third pair with a1-a0 set to 10, and the fourth pair with a1-a0 set to 11. in double byte program the first pair of nibbles is that at the address with a0 set to 0, the second pair with a0 set to 1) previous +1 1 tar 1111b i the host drives fwh0-fwh3 to 1111b to indicate a turnaround cycle. previous +1 1tar 1111b (float) o the fwh flash memory takes control of fwh0-fwh3 during this cycle. previous +1 1 sync 0000b o the fwh flash memory drives fwh0-fwh3 to 0000b, indicating it has received data or a command. previous +1 1 tar 1111b o the fwh flash memory drives fwh0-fwh3 to 1111b, indicating a turnaround cycle. previous +1 1tar 1111b (float) n/a the fwh flash memory floats its outputs and the host takes control of fwh0-fwh3. ai08434b clk fwh4 fwh0-fwh3 number of clock cycles start idsel addr msize data tar sync tar 1171m212
m50flw080a, m50flw080b 16/53 table 8. lpc bus read field definitions (1-byte) figure 9. lpc bus read waveforms (1-byte) clock cycle number clock cycle count field lad0- lad3 memory i/o description 1 1 start 0000b i on the rising edge of clk with lframe low, the contents of lad0-lad3 must be 0000b to indicate the start of a lpc cycle. 21 cyctype + dir 0100b i indicates the type of cycle and selects 1-byte reading. bits 3:2 must be 01b. bit 1 indicates the direction of transfer: 0b for read. bit 0 is don?t care. 3-10 8 addr xxxx i a 32-bit address is transferred, with the most significant nibble first. a23-a31 must be set to 1. a22=1 for memory access, and a22=0 for register access. table 5. shows the appropriate values for a21-a20. 11 1 tar 1111b i the host drives lad0-lad3 to 1111b to indicate a turnaround cycle. 12 1 tar 1111b (float) o the lpc flash memory takes control of lad0-lad3 during this cycle. 13-14 2 wsync 0101b o the lpc flash memory drives lad0-lad3 to 0101b (short wait-sync) for two clock cycles, indicating that the data is not yet available. two wait-states are always included. 15 1 rsync 0000b o the lpc flash memory drives lad0-lad3 to 0000b, indicating that data will be available during the next clock cycle. 16-17 2 data xxxx o data transfer is two clk cycles, starting with the least significant nibble. 18 1 tar 1111b o the lpc flash memory drives lad0-lad3 to 1111b to indicate a turnaround cycle. 19 1 tar 1111b (float) n/a the lpc flash memory floats its outputs, the host takes control of lad0-lad3. ai04429 clk lframe lad0-lad3 number of clock cycles start cyctype + dir addr tar sync data tar 1182322
17/53 m50flw080a, m50flw080b table 9. lpc bus write field definitions (1 byte) figure 10. lpc bus write waveforms (1 byte) table 10. a/a mux bus operations clock cycle number clock cycle count field lad0- lad3 memory i/o description 1 1 start 0000b i on the rising edge of clk with lframe low, the contents of lad0-lad3 must be 0000b to indicate the start of a lpc cycle. 21 cycty pe + dir 011xb i indicates the type of cycle. bits 3:2 must be 01b. bit 1 indicates the direction of transfer: 1b for write. bit 0 is don?t care (x). 3-10 8 addr xxxx i a 32-bit address is transferred, with the most significant nibble first. a23-a31 must be set to 1. a22=1 for memory access, and a22=0 for register access. table 5. shows the appropriate values for a21-a20. 11-12 2 data xxxx i data transfer is two cycles, starting with the least significant nibble. 13 1 tar 1111b i the host drives lad0-lad3 to 1111b to indicate a turnaround cycle. 14 1 tar 1111b (float) o the lpc flash memory takes control of lad0-lad3 during this cycle. 15 1 sync 0000b o the lpc flash memory drives lad0-lad3 to 0000b, indicating it has received data or a command. 16 1 tar 1111b o the lpc flash memory drives lad0-lad3 to 1111b, indicating a turnaround cycle. 17 1 tar 1111b (float) n/a the lpc flash memory floats its outputs and the host takes control of lad0-lad3. operation g w rp v pp dq7-dq0 bus read v il v ih v ih don't care data output bus write v ih v il v ih v cc or v pph data input output disable v ih v ih v ih don't care hi-z reset v il or v ih v il or v ih v il don't care hi-z ai04430 clk lframe lad0-lad3 number of clock cycles start cyctype + dir addr data tar sync tar 1182212
m50flw080a, m50flw080b 18/53 command interface all bus write operations to the device are inter- preted by the command interface. commands consist of one or more sequential bus write oper- ations. an internal program/erase controller han- dles all timings, and verifies the correct execution of the program and erase commands. the pro- gram/erase controller provides a status register whose output may be read at any time to monitor the progress or the result of the operation. the command interface reverts to the read mode when power is first applied, or when exiting from reset. command sequences must be followed ex- actly. any invalid combination of commands will be ignored. see table 11. for the available command codes. table 11. command codes the following commands are the basic commands used to read from, write to, and configure the de- vice. the following text descriptions should be read in conjunction with table 13. . read memory array command. the read memory array command returns the device to its read mode, where it behaves like a rom or eprom. one bus write cycle is required to issue the read memory array command and return the device to read mode. once the command is is- sued, the device remains in read mode until an- other command is issued. from read mode, bus read operations access the memory array. if the program/erase controller is executing a pro- gram or erase operation, the device will not accept any read memory array commands until the oper- ation has completed. for a multibyte read, in the fwh mode, the ad- dress, that was transmitted with the command, will be automatically aligned, according to the msize granularity. for example, if msize=7, regardless of any values that are provided for a6-a0, the first output will be from the location for which a6-a0 are all ?0?s. read status register command. the read status register command is used to read the sta- tus register. one bus write cycle is required to is- sue the read status register command. once the command is issued, subsequent bus read opera- tions read the status register until another com- mand is issued. see the section on the status register for details on the definitions of the status register bits. read electronic signature command. the read electronic signature command is used to read the manufacturer code and the device code. one bus write cycle is required to issue the read electronic signature command. once the com- mand is issued, the manufacturer code and de- vice code can be read using conventional bus read operations, and the addresses shown in ta- ble 12. . table 12. electronic signature codes note: 1. a22 should be ?1?, and the id lines and upper address bits should be set according to the rules illustrated in table 5. , table 6. and table 8. . the device remains in this mode until another command is issued. that is, subsequent bus read operations continue to read the manufactur- er code, or the device code, and not the memory array. program command. the program command can be used to program a value to one address in the memory array at a time. the program command works by changing appro- priate bits from ?1? to ?0?. (it cannot change a bit from ?0? back to ?1?. attempting to do so will not modify the value of the bit. only the erase com- mand can set bits back to ?1?. and does so for all of the bits in the block.) two bus write operations are required to issue the program command. the second bus write cycle latches the address and data, and starts the pro- gram/erase controller. hexa- decimal command 10h alternative program setup, double/ quadruple byte program setup, chip erase confirm 20h block erase setup 32h sector erase setup 40h program, double/quadruple byte program setup 50h clear status register 70h read status register 80h chip erase setup 90h read electronic signature b0h program/erase suspend d0h program/erase resume, block erase confirm, sector erase confirm ffh read memory array code address 1 data manufacturer code ...00000h 20h device code m50flw080a m50flw080b ...00001h 80h 81h
19/53 m50flw080a, m50flw080b once the command is issued, subsequent bus read operations read the value in the status reg- ister. (see the section on the status register for details on the definitions of the status register bits.) if the address falls in a protected block, the pro- gram operation will abort, the data in the memory array will not be changed, and the status register will indicate the error. during the program operation, the memory will only accept the read status register command and the program/erase suspend command. all other commands are ignored. see figure 22. , for a suggested flowchart on using the program command. typical program times are given in table 18. . quadruple byte program command (a/a mux interface). the quadruple byte program com- mand is used to program four adjacent bytes in the memory array at a time. the four bytes must differ only for addresses a0 and a1. programming should not be attempted when v pp is not at v pph . five bus write operations are required to issue the command. the second, third and fourth bus write cycles latch the respective addresses and data of the first, second and third bytes in the program/ erase controller. the fifth bus write cycle latches the address and data of the fourth byte and starts the program/erase controller. once the command is issued, subsequent bus read operations read the value in the status register. (see the section on the status register for details on the definitions of the status register bits.) during the quadruple byte program operation, the memory will only accept the read status register and program/erase suspend commands. all other commands are ignored. note that the quadruple byte program command cannot change a bit set to ?0? back to ?1? and at- tempting to do so will not modify its value. one of the erase commands must be used to set all of the bits in the block to ?1?. see figure 24. , for a suggested flowchart on using the quadruple byte program command. typical quadruple byte program times are given in table 18. . double/quadruple byte program command (fwh mode). the double/quadruple byte pro- gram command can be used to program two/four adjacent bytes to the memory array at a time. the two bytes must differ only for address a0; the four bytes must differ only for addresses a0 and a1. two bus write operations are required to issue the command. the second bus write cycle latches the start address and two/four data bytes and starts the program/erase controller. once the command is issued, subsequent bus read operations read the contents of the status register. (see the sec- tion on the status register for details on the defi- nitions of the status register bits.) during the double/quadruple byte program oper- ation the memory will only accept the read status register and program/erase suspend commands. all other commands are ignored. note that the double/quadruple byte program command cannot change a bit set to ?0? back to ?1? and attempting to do so will not modify its value. one of the erase commands must be used to set all of the bits in the block to ?1?. see figure 23. , for a suggested flowchart on using the double/quadruple byte program command. typical double/quadruple byte program times are given in table 18. . chip erase command. the chip erase com- mand erases the entire memory array, setting all of the bits to ?1?. all previous data in the memory array are lost. this command, though, is only available under the a/a mux interface. two bus write operations are required to issue the command, and to start the program/erase con- troller. once the command is issued, subsequent bus read operations read the contents of the sta- tus register. (see the section on the status reg- ister for details on the definitions of the status register bits.) erasing should not be attempted when v pp is not at v pph , otherwise the result is uncertain. during the chip erase operation, the memory will only accept the read status register command. all other commands are ignored. see figure 26. , for a suggested flowchart on using the chip erase command. typical chip erase times are given in table 18. . block erase command. the block erase com- mand is used to erase a block, setting all of the bits to ?1?. all previous data in the block are lost. two bus write operations are required to issue the command. the second bus write cycle latches the block address and starts the program/erase con- troller. once the command is issued, subsequent bus read operations read the contents of the sta- tus register. (see the section on the status reg- ister for details on the definitions of the status register bits.) if the block, or if at least one sector of the block (for the blocks that are split into sectors), is protected (fwh/lpc only) then the block erase operation will abort, the data in the block will not be changed, and the status register will indicate the error. during the block erase operation the memory will only accept the read status register and pro- gram/erase suspend commands. all other com- mands are ignored.
m50flw080a, m50flw080b 20/53 see figure 27. , for a suggested flowchart on using the block erase command. typical block erase times are given in table 18. . sector erase command. the sector erase command is used to erase a uniform 4-kbyte sec- tor, setting all of the bits to ?1?. all previous data in the sector are lost. two bus write operations are required to issue the command. the second bus write cycle latches the sector address and starts the program/erase controller. once the command is issued, subse- quent bus read operations read the contents of the status register. (see the section on the status register for details on the definitions of the status register bits.) if the sector is protected (fwh/lpc only), the sector erase operation will abort, the data in the sector will not be changed, and the status regis- ter will indicate the error. during the sector erase operation the memory will only accept the read status register and pro- gram/erase suspend commands. all other com- mands are ignored. see figure 27. , for a suggested flowchart on using the sector erase command. typical sector erase times are given in table 18. . clear status register command. the clear status register command is used to reset status register bits sr1, sr3, sr4 and sr5 to ?0?. one bus write is required to issue the command. once the command is issued, the device returns to its previous mode, subsequent bus read operations continue to output the data from the same area, as before. once set, these status register bits remain set. they do not automatically return to ?0?, for exam- ple, when a new program or erase command is is- sued. if an error has occurred, it is essential that any error bits in the status register are cleared, by issuing the clear status register command, be- fore attempting a new program or erase com- mand. program/erase suspend command. the pro- gram/erase suspend command is used to pause the program/erase controller during a program or sector/block erase operation. one bus write cy- cle is required to issue the command. once the command has been issued, it is neces- sary to poll the program/erase controller status bit until the program/erase controller has paused. no other commands are accepted until the pro- gram/erase controller has paused. after the pro- gram/erase controller has paused, the device continues to output the contents of the status reg- ister until another command is issued. during the polling period, between issuing the pro- gram/erase suspend command and the program/ erase controller pausing, it is possible for the op- eration to complete. once the program/erase controller status bit indicates that the program/ erase controller is no longer active, the program suspend status bit or the erase suspend status bit can be used to determine if the operation has completed or is suspended. during program/erase suspend, the read memo- ry array, read status register, read electronic signature and program/erase resume com- mands will be accepted by the command inter- face. additionally, if the suspended operation was sector erase or block erase then the program command will also be accepted. however, it should be noted that only the sectors/blocks not being erased may be read or programmed correct- ly. see figure 25. , and figure 28. , for suggested flowcharts on using the program/erase suspend command. typical times and delay durations are given in table 18. . program/erase resume command. the pro- gram/erase resume command can be used to re- start the program/erase controller after a program/erase suspend has paused it. one bus write cycle is required to issue the command. once the command is issued, subsequent bus read operations read the contents of the status register.
21/53 m50flw080a, m50flw080b table 13. commands note: 1. for all commands: the first cycle is a write. for the first three commands (re ad memory, read status register, read elec tronic signature), the second and next cycles are read. for the remaining commands, the second and next cycles are write. ba = any address in the block, sa = any address in the sector. x = don?t care, except that a22=1 (for fwh or lpc mode), and a21 and a20 are set according to the rules shown in table 5. (for lpc mode) 2. after a read memory array command, read the memory as normal until another command is issued. 3. after a read status register command, read the status register as normal until another command is issued. 4. after the erase and program commands read the status register until the command completes and another command is issued. 5. after the clear status register command bits sr1, sr 3, sr4 and sr5 in the status register are reset to ?0?. 6. while an operation is being program/erase suspended, the read memory array, read status register, program (during erase suspend) and program/erase resume commands can be issued. 7. the program/erase resume command causes the program/erase suspended operation to resume. read the status register until the program/erase controller completes and the memory returns to read mode. 8. do not use invalid or reserved commands. 9. multiple byte program pa= start address, a0 (double byte pr ogram) a0 and a1 (quadruple byte program) are don`t care. pd is two or four bytes depending on msize code. 10. ?1+? indicates that there is one write cycle, followed by any number of read cycles. 11. configuration registers are accessed directly without using any specific command code. a single bus write or bus read operat ion is all that is needed. 12. addresses a1, a2, a3 and a4 must be consecutive addresses, differing only in address bits a0 and a1. command cycle bus operations (1) 1st 2nd 3rd 4th 5th addr data addr data addr data addr data addr data read memory array (2,10,11) 1+ x ffh read addr read data (read addr2) (read data2) (read addr3) (read data3) (read addr4) (read data4) read status register (3,10) 1+ x 70h x status reg (x) (status reg) (x) (status reg) (x) (status reg) read electronic signature (10) 1+ x 90h or 98h sig addr signat ure (sig addr) (signat ure) (sig addr) (signat ure) (sig addr) (signat ure) program / multiple byte program (fwh) (4,9,11) 2x 40h or 10h prog addr prog data quadruple byte program (a/a mux) (4,12) 5x 30ha1 prog data1 a2 prog data2 a3 prog data3 a4 prog data4 chip erase (4) 2x 80h x 10h block erase (4) 2 x 20h ba d0h sector erase (4) 2 x 32h sa d0h clear status register (5) 1x 50h program/erase suspend (6) 1x b0h program/erase resume (7) 1x d0h invalid reserved (8) 1x 00h 1x 01h 1x 60h 1x 2fh 1x c0h
m50flw080a, m50flw080b 22/53 status register the status register provides information on the current or previous program or erase operation. the bits in the status register convey specific in- formation about the progress of the operation. to read the status register, the read status reg- ister command can be issued. the status register is automatically read after program, erase and program/erase resume commands are issued. the status register can be read from any ad- dress. the text descriptions, below, should be read in conjunction with table 14. , where the meanings of the status register bits are summarized. program/erase controller status (bit sr7). this bit indicates whether the program/erase con- troller is active or inactive. when the program/ erase controller status bit is ?0?, the program/ erase controller is active; when the bit is ?1?, the program/erase controller is inactive. the program/erase controller status is ?0? imme- diately after a program/erase suspend command is issued, until the program/erase controller paus- es. after the program/erase controller pauses, the bit is ?1?. the end of a program and erase operation can be found by polling the program/erase controller status bit can be polled. the other bits in the sta- tus register should not be tested until the pro- gram/erase controller has completed the operation (and the program/erase controller sta- tus bit is ?1?). after the program/erase controller has completed its operation, the erase status, program status, v pp status and block/sector protection status bits should be tested for errors. erase suspend status (bit sr6). this bit indi- cates that an erase operation has been suspend- ed, and that it is waiting to be resumed. the erase suspend status should only be considered valid when the program/erase controller status bit is ?1? (program/erase controller inactive). after a pro- gram/erase suspend command is issued, the memory may still complete the operation rather than entering the suspend mode. when the erase suspend status bit is ?0?, the pro- gram/erase controller is active or has completed its operation. when the bit is ?1?, a program/erase suspend command has been issued and the memory is waiting for a program/erase resume command. when a program/erase resume command is is- sued, the erase suspend status bit returns to ?0?. erase status (bit sr5). this bit indicates if a problem has occurred during the erasing of a sec- tor or block. the erase status bit should be read once the program/erase controller status bit is ?1? (program/erase controller inactive). when the erase status bit is ?0?, the memory has successfully verified that the sector/block has been erased correctly. when the erase status bit is ?1?, the program/erase controller has applied the maximum number of pulses to the sector/ block and still failed to verify that the sector/block has been erased correctly. once the erase status bit is set to ?1?, it can only be reset to ?0? by a clear status register com- mand, or by a hardware reset. if it is set to ?1?, it should be reset before a new program or erase command is issued, otherwise the new command will appear to have failed, too. program status (bit sr4). this bit indicates if a problem has occurred during the programming of a byte. the program status bit should be read once the program/erase controller status bit is ?1? (program/erase controller inactive). when the program status bit is ?0?, the memory has successfully verified that the byte has been programmed correctly. when the program status bit is ?1?, the program/erase controller has applied the maximum number of pulses to the byte and still failed to verify that the byte has been programmed correctly. once the program status bit is set to ?1?, it can only be reset to ?0? by a clear status register com- mand, or by a hardware reset. if it is set to ?1?, it should be reset before a new program or erase command is issued, otherwise the new command will appear to have failed, too. v pp status (bit sr3). this bit indicates whether an invalid voltage was detected on the v pp pin at the beginning of a program or erase operation. the v pp pin is only sampled at the beginning of the operation. indeterminate results can occur if v pp becomes invalid during a program or erase operation. once the v pp status bit set to ?1?, it can only be re- set to ?0? by a clear status register command, or by a hardware reset. if it is set to ?1?, it should be reset before a new program or erase command is issued, otherwise the new command will appear to have failed, too. program suspend status (bit sr2). this bit in- dicates that a program operation has been sus- pended, and that it is waiting to be resumed. the program suspend status should only be consid- ered valid when the program/erase controller sta- tus bit is ?1? (program/erase controller inactive). after a program/erase suspend command is is- sued, the memory may still complete the operation instead of entering the suspend mode.
23/53 m50flw080a, m50flw080b when the program suspend status bit is ?0?, the program/erase controller is active, or has com- pleted its operation. when the bit is ?1?, a program/ erase suspend command has been issued and the memory is waiting for a program/erase re- sume command. when a program/erase resume command is is- sued, the program suspend status bit returns to ?0?. block/sector protection status (bit sr1). the block/sector protection status bit can be used to identify if the program or erase operation has tried to modify the contents of a protected block or sec- tor. when the block/sector protection status bit is reset to ?0?, no program or erase operations have been attempted on protected blocks or sectors since the last clear status register command or hardware reset. when the block/sector protection status bit is ?1?, a program or erase operation has been attempted on a protected block or sector. once it is set to ?1?, the block/sector protection status bit can only be reset to ?0? by a clear status register command or by a hardware reset. if it is set to ?1?, it should be reset before a new program or erase command is issued, otherwise the new command will appear to have failed, too. using the a/a mux interface, the block/sector pro- tection status bit is always ?0?. reserved (bit sr0). bit 0 of the status register is reserved. its value should be masked. table 14. status register bits note: 1. for program operations during erase suspend, the sr6 bit is ?1?, otherwise the sr6 bit is ?0?. operation sr7 sr6 sr5 sr4 sr3 sr2 sr1 program active ?0? x (1) ?0? ?0? ?0? ?0? ?0? program suspended ?1 x (1) ?0? ?0? ?0? ?1? ?0? program completed successfully ?1? x (1) ?0? ?0? ?0? ?0? ?0? program failure due to v pp error ?1? x (1) ?0? ?1? ?1? ?0? ?0? program failure due to block/sector protection (fwh/lpc interface only) ?1? x (1) ?0? ?1? ?0? ?0? ?1? program failure due to cell failure ?1? x (1) ?0? ?1? ?0? ?0? ?0? erase active ?0? ?0? ?0? ?0? ?0? ?0? ?0? erase suspended ?1? ?1? ?0? ?0? ?0? ?0? ?0? erase completed successfully ?1? ?0? ?0? ?0? ?0? ?0? ?0? erase failure due to v pp error ?1? ?0? ?1? ?0? ?1? ?0? ?0? erase failure due to block/sector protection (fwh/lpc interface only) ?1? ?0? ?1? ?0? ?0? ?0? ?1? erase failure due to failed cell(s) in block or sector ?1? ?0? ?1? ?0? ?0? ?0? ?0?
m50flw080a, m50flw080b 24/53 firmware hub/low pin count (fwh/lpc) interface configuration registers when the firmware hub interface/low pin count is selected, several additional registers can be ac- cessed. these registers control the protection sta- tus of the blocks/sectors, read the general purpose input pins and identify the memory using the manufacturer code. see table 15. for the memory map of the configuration registers. the configuration registers are accessed directly with- out using any specific command code. a single bus write or bus read operation, with the appro- priate address (including a22=0), is all that is needed. lock registers the lock registers control the protection status of the blocks/sectors. each block/sector has its own lock register. three bits within each lock regis- ter control the protection of each block/sector: the write lock bit, the read lock bit and the lock down bit. the lock registers can be read and written. care should be taken, though, when writing. once the lock down bit is set, ?1?, further modifications to the lock register cannot be made until it is cleared again by a reset or power-up. see table 16. for details on the bit definitions of the lock registers. write lock. the write lock bit determines whether the contents of the block/sector can be modified (using the program or erase command). when the write lock bit is set, ?1?, the block/sec- tor is write protected ? any operations that attempt to change the data in the block/sector will fail, and the status register will report the error. when the write lock bit is reset, ?0?, the block/sector is not write protected by the lock register, and may be modified, unless it is write protected by some other means. if the top block lock signal, tbl , is low, v il , then the top block (block 15) is write protected, and cannot be modified. similarly, if the write protect signal, wp , is low, v il , then the main blocks (blocks 0 to 14) are write protected, and cannot be modified. for details, see appendix a. and table 16. . after power-up, or reset, the write lock bit is al- ways set to ?1? (write-protected). read lock. the read lock bit determines whether the contents of the block/sector can be read (in read mode). when the read lock bit is set, ?1?, the block/sector is read protected ? any operation that attempts to read the contents of the block/sector will read 00h instead. when the read lock bit is reset, ?0?, read operations are al- lowed in the block/sector, and return the value of the data that had been programmed in the block/ sector. after power-up, or reset, the read lock bit is al- ways reset to ?0? (not read-protected). lock down. the lock down bit provides a mechanism for protecting software data from sim- ple hacking and malicious attack. when the lock down bit is set, ?1?, further modification to the write lock, read lock and lock down bits cannot be performed. a reset, or power-up, is required be- fore changes to these bits can be made. when the lock down bit is reset, ?0?, the write lock, read lock and lock down bits can be changed. table 15. configuration register map note: in lpc mode, a most significant nibble, f, must be added to the memory address. for all registers, a22=0, and the remainin g address bits should be set according to the rules shown in the addr field of table 6. to table 9. . mnemonic register name memory address default value access lock registers (for details, see appendix a. ) gpi_reg firmware hub/low pin count (fwh/lpc) general purpose input register fbc0100h n/a r manu_reg manufacturer code register fbc0000h 20h r
25/53 m50flw080a, m50flw080b table 16. lock register bit definitions note: 1. applies to the registers that are defined in table 34. and table 35. . table 17. general purpose inputs register definition note: 1. applies to the general purpose inputs register (gpi-reg). firmware hub/low pin count (fwh/lpc) general purpose input register the fwh/lpc general purpose input register holds the state of the general purpose input pins, gpi0-gpi4. when this register is read, the state of these pins is returned. this register is read-only. writing to it has no effect. the signals on the fwh/lpc interface general purpose input pins should remain constant throughout the whole bus read cycle. manufacturer code register reading the manufacturer code register returns the value 20h, which is the manufacturer code for stmicroelectronics. this register is read-only. writing to it has no effect. bit bit name value function (1) 7-3 reserved 2 read-lock ?1? bus read operations in this block or sector always return 00h. ?0? bus read operations in this block or sector return the memory array contents. (default value). 1 lock-down ?1? changes to the read-lock bit and the write-lock bit cannot be performed. once a ?1? is written to the lock-down bit it cannot be cleared to ?0?; the bit is always reset to ?0? following a reset (using rp or init ) or after power-up. ?0? read-lock and write-lock can be changed by writing new values to them. (default value). 0write-lock ?1? program and erase operations in this block or sector will set an error in the status register. the memory contents will not be changed. (default value). ?0? program and erase operations in this block or sector are executed and will modify the block or sector contents. bit bit name value function (1) 7-5 reserved 4gpi4 ?1? input pin gpi4 is at v ih ?0? input pin gpi4 is at v il 3gpi3 ?1? input pin gpi3 is at v ih ?0? input pin gpi3 is at v il 2gpi2 ?1? input pin gpi2 is at v ih ?0? input pin gpi2 is at v il 1gpi1 ?1? input pin gpi1 is at v ih ?0? input pin gpi1 is at v il 0gpi0 ?1? input pin gpi0 is at v ih ?0? input pin gpi0 is at v il
m50flw080a, m50flw080b 26/53 program and erase times the program and erase times are shown in table 18. . table 18. program and erase times note: 1. t a = 25c, v cc = 3.3v 2. sampled only, not 100% tested. 3. time to program two bytes. 4. time to program four bytes. 5. time obtained executing the quadruple byte program command. parameter interface test condition min typ (1) max unit byte program 10 200 s double byte program fwh v pp = 12v 5% 10 (3) 200 s quadruple byte program a/a multiplexed fwh v pp = 12v 5% 10 (4) 200 s block program v pp = 12v 5% 0.1 (5) 5 s v pp = v cc 0.4 5 sector erase (4 kbytes) (2) v pp = 12v 5% 0.4 4 s v pp = v cc 0.5 5 block erase (64 kbytes) v pp = 12v 5% 0.75 8 s v pp = v cc 110 chip erase a/a multiplexed v pp = 12v 5% 10 s program/erase suspend to program pause (2) 5 s program/erase suspend to block erase/ sector erase pause (2) 30 s
27/53 m50flw080a, m50flw080b maximum rating stressing the device above the rating listed in the absolute maximum ratings table may cause per- manent damage to the device. these are stress ratings only and operation of the device at these or any other conditions above those indicated in the operating sections of this specification is not im- plied. exposure to absolute maximum rating con- ditions for extended periods may affect device reliability. refer also to the stmicroelectronics sure program and other relevant quality docu- ments. table 19. absolute maximum ratings note: 1. compliant with jedec std j-std-020b (for small body, sn-pb or pb assembly), the st ecopack ? 7191395 specification, and the european directive on restrictions on hazardous substances (rohs) 2002/95/eu 2. minimum voltage may undershoot to ?2v for less than 20ns during transitions. maximum voltage may overshoot to v cc + 2v for less than 20ns during transitions. 3. jedec std jesd22-a114a (c1=100 pf, r1=1500 ? , r2=500 ? ) symbol parameter min. max. unit t stg storage temperature ?65 150 c t lead lead temperature during soldering see note 1 c v io input or output range 2 ?0.50 v cc + 0.6 v v cc supply voltage ?0.50 4 v v pp program voltage ?0.6 13 v v esd electrostatic discharge voltage (human body model) 3 ?2000 2000 v
m50flw080a, m50flw080b 28/53 dc and ac parameters this section summarizes the operating measure- ment conditions, and the dc and ac characteris- tics of the device. the parameters in the dc and ac characteristics tables that follow, are derived from tests performed under the measurement conditions summarized in table 20. , table 21. and table 22. . designers should check that the operating conditions in their circuit match the oper- ating conditions when relying on the quoted pa- rameters. table 20. operating conditions table 21. fwh/lpc interface ac measurement conditions table 22. a/a mux interface ac measurement conditions figure 11. fwh/lpc interface ac measurement i/o waveforms symbol parameter min. max. unit v cc supply voltage 3.0 3.6 v t a ambient operating temperature ?20 85 c parameter value unit load capacitance (c l ) 10 pf input rise and fall times 1.4 ns input pulse voltages 0.2 v cc and 0.6 v cc v input and output timing ref. voltages 0.4 v cc v parameter value unit load capacitance (c l ) 30 pf input rise and fall times 10 ns input pulse voltages 0 to 3 v input and output timing ref. voltages 1.5 v ai03404 0.6 v cc 0.2 v cc 0.4 v cc i o > i lo i o < i lo i o < i lo input and output ac testing waveform output ac tri-state testing waveform
29/53 m50flw080a, m50flw080b figure 12. a/a mux interface ac measurement i/o waveform figure 13. ac measurement load circuit table 23. impedance note: 1. sampled only, not 100% tested. 2. see pci specification. 3. t a = 25c, f = 1mhz. symbol parameter test condition min max unit c in (1) input capacitance v in = 0v 13 pf c clk (1) clock capacitance v in = 0v 312pf l pin (2) recommended pin inductance 20 nh ai01417 3v 0v 1.5v ai08430 v dd c l c l includes jig capacitance 16.7k ? device under test 0.1f v dd 0.1f v pp 16.7k ?
m50flw080a, m50flw080b 30/53 table 24. dc characteristics note: 1. sampled only, not 100% tested. 2. input leakage currents include high-z output leakage for all bi-directional buffers with tri-state outputs. 3. id0 and id1 are rfu in lpc mode. symbol parameter interface test condition min max unit v ih input high voltage fwh 0.5 v cc v cc + 0.5 v a/a mux 0.7 v cc v cc + 0.3 v v il input low voltage fwh/lpc ?0.5 0.3 v cc v a/a mux -0.5 0.8 v v ih (init ) init input high voltage fwh/lpc 1.1 v cc + 0.5 v v il (init ) init input low voltage fwh/lpc ?0.5 0.2 v cc v i li (2) input leakage current 0v v in v cc 10 a i li2 ic, idx input leakage current ic, id0, id1, id2, id3 (3) = v cc 200 a r il ic, idx input pull low resistor 20 100 k ? v oh output high voltage fwh/lpc i oh = ?500 a 0.9 v cc v a/a mux i oh = ?100 a v cc ? 0.4 v v ol output low voltage fwh/lpc i ol = 1.5ma 0.1 v cc v a/a mux i ol = 1.8ma 0.45 v i lo output leakage current 0v v out v cc 10 a v pp1 v pp voltage 33.6v v pph v pp voltage (fast erase) 11.4 12.6 v v lko (1) v cc lockout voltage 1.8 2.3 v i cc1 supply current (standby) fwh/lpc fwh4/lframe = 0.9v cc v pp = v cc all other inputs 0.9v cc to 0.1v cc v cc = 3.6v, f(clk) = 33mhz 100 a i cc2 supply current (standby) fwh/lpc fwh4/lframe = 0.1 v cc , v pp = v cc all other inputs 0.9 v cc to 0.1 v cc v cc = 3.6v, f(clk) = 33mhz 10 ma i cc3 supply current (any internal operation active) fwh/lpc v cc = v cc max, v pp = v cc f(clk) = 33mhz i out = 0ma 60 ma i cc4 supply current (read) a/a mux g = v ih , f = 6mhz 20 ma i cc5 (1) supply current (program/erase) a/a mux program/erase controller active 20 ma i pp v pp supply current (read/standby) v pp > v cc 400 a i pp1 (1) v pp supply current (program/erase active) v pp = v cc 40 ma v pp = 12v 5% 15 ma
31/53 m50flw080a, m50flw080b figure 14. fwh/lpc interface clock waveform table 25. fwh/lpc interface clock characteristics note: 1. devices on the pci bus must work with any clock frequency between dc and 33mhz. below 16mhz devices may be guaranteed by design rather than tested. refer to pci specification. symbol parameter test condition value unit t cyc clk cycle time (1) min 30 ns t high clk high time min 11 ns t low clk low time min 11 ns clk slew rate peak to peak min 1 v/ns max 4 v/ns ai03403 thigh tlow 0.6 v cc tcyc 0.5 v cc 0.4 v cc 0.3 v cc 0.2 v cc 0.4 v cc , p-to-p (minimum)
m50flw080a, m50flw080b 32/53 figure 15. fwh/lpc interface ac signal timing waveforms table 26. fwh/lpc interface ac signal timing characteristics note: 1. the timing measurements for active/float transitions are defined when the current through the pin equals the leakage cur rent spec- ification. 2. applies to all inputs except clk and fwh4. symbol pci symbol parameter value unit t chqv t val clk to data out min 2 ns max 11 ns t chqx (1) t on clk to active (float to active delay) min 2 ns t chqz t off clk to inactive (active to float delay) max 28 ns t avch t dvch t su input set-up time (2) min 7 ns t chax t chdx t h input hold time (2) min 0 ns t flch input set-up time on fwh4 min 10 ns t chfh input hold time on fwh4 min 5 ns clk fwh0-fwh3/ lad0-lad3 valid tchqv tchqz tchqx tchdx tdvch valid output data float output data valid input data ai09700 tchfh tflch fwh4 start cycle
33/53 m50flw080a, m50flw080b figure 16. reset ac waveforms table 27. reset ac characteristics note: 1. see chapter 4 of the pci specification. symbol parameter test condition value unit t plph rp or init reset pulse width min 100 ns rp or init slew rate (1) rising edge only min 50 mv/ns t phfl rp or init high to fwh4/ lframe low fwh/lpc interface only min 30 s t phwl t phgl rp high to write enable or output enable low a/a mux interface only min 50 s rp, int ai09705 w, g, fwh4/lframe tplph tphwl, tphgl, tphfl
m50flw080a, m50flw080b 34/53 figure 17. a/a mux interface read ac waveforms table 28. a/a mux interface read ac characteristics note: 1. g may be delayed up to t chqv ? t glqv after the rising edge of rc without impact on t chqv . symbol parameter test condition value unit t avav read cycle time min 250 ns t avcl row address valid to rc low min 50 ns t clax rc low to row address transition min 50 ns t avch column address valid to rc high min 50 ns t chax rc high to column address transition min 50 ns t chqv (1) rc high to output valid max 150 ns t glqv (1) output enable low to output valid max 50 ns t phav rp high to row address valid min 1 s t glqx output enable low to output transition min 0 ns t ghqz output enable high to output hi-z max 50 ns t ghqx output hold from output enable high min 0 ns ai03406 tavav tclax tchax tglqx tglqv tghqx valid a0-a10 g dq0-dq7 rc tchqv tghqz column addr valid w rp tphav row addr valid next addr valid tavcl tavch
35/53 m50flw080a, m50flw080b figure 18. a/a mux interface write ac waveforms table 29. a/a mux interface write ac characteristics note: 1. sampled only, not 100% tested. 2. applicable if v pp is seen as a logic input (v pp < 3.6v). symbol parameter test condition value unit t wlwh write enable low to write enable high min 100 ns t dvwh data valid to write enable high min 50 ns t whdx write enable high to data transition min 5 ns t avcl row address valid to rc low min 50 ns t clax rc low to row address transition min 50 ns t avch column address valid to rc high min 50 ns t chax rc high to column address transition min 50 ns t whwl write enable high to write enable low min 100 ns t chwh rc high to write enable high min 50 ns t vphwh (1) v pp high to write enable high min 100 ns t whgl write enable high to output enable low min 30 ns t whrl write enable high to rb low min 0 ns t qvvpl (1,2) output valid, rb high to v pp low min 0 ns ai04185 tclax tchax twhdx tdvwh valid srd a0-a10 g dq0-dq7 rc tchwh c1 w r1 tavcl tavch r2 c2 twlwh twhwl v pp tvphwh twhgl tqvvpl d in1 d in2 write erase or program setup write erase confirm or valid address and data automated erase or program delay read status register data ready to write another command
m50flw080a, m50flw080b 36/53 package mechanical figure 19. plcc32 ? 32 pin rectangular plastic leaded chip carrier, package outline note: drawing is not to scale. plcc-a d e3 e1 e 1 n d1 d3 cp b e2 e b1 a1 a r 0.51 (.020) 1.14 (.045) f a2 e2 d2 d2
37/53 m50flw080a, m50flw080b table 30. plcc32 ? 32 pin rectangular plastic leaded chip carrier, package mechanical data symbol millimeters inches typ min max typ min max a 3.18 3.56 0.125 0.140 a1 1.53 2.41 0.060 0.095 a2 0.38 ? 0.015 ? b 0.33 0.53 0.013 0.021 b1 0.66 0.81 0.026 0.032 cp 0.10 0.004 d 12.32 12.57 0.485 0.495 d1 11.35 11.51 0.447 0.453 d2 4.78 5.66 0.188 0.223 d3 7.62 ? ? 0.300 ? ? e 14.86 15.11 0.585 0.595 e1 13.89 14.05 0.547 0.553 e2 6.05 6.93 0.238 0.273 e310.16? ?0.400? ? e 1.27 ? ? 0.050 ? ? f 0.00 0.13 0.000 0.005 r 0.89 ? ? 0.035 ? ? n32 32
m50flw080a, m50flw080b 38/53 figure 20. tsop32 ? 32 lead plastic thin small outline, 8x14 mm, package outline note: drawing is not to scale. table 31. tsop32 ? 32 lead plastic thin small outline, 8x14 mm, package mechanical data symbol millimeters inches typ min max typ min max a 1.200 0.0472 a1 0.050 0.150 0.0020 0.0059 a2 0.950 1.050 0.0374 0.0413 05 05 b 0.170 0.270 0.0067 0.0106 c 0.100 0.210 0.0039 0.0083 cp 0.100 0.0039 d 13.800 14.200 0.5433 0.5591 d1 12.300 12.500 0.4843 0.4921 e 0.500 ? ? 0.0197 ? ? e 7.900 8.100 0.3110 0.3189 l 0.500 0.700 0.0197 0.0276 n32 32 tsop-a d1 e 1 n cp b e a2 a n/2 d die c l a1
39/53 m50flw080a, m50flw080b figure 21. tsop40 ? 40 lead plastic thin small outline, 10 x 20mm, package outline note: drawing is not to scale. table 32. tsop40 ? 40 lead plastic thin small outline, 10 x 20mm, package mechanical data symbol millimeters inches typ min max typ min max a1.200 0 a1 0.050 0.150 0 0 a2 0.950 1.050 0 0 b 0.170 0.270 0 0 c 0.100 0.210 0 0 cp 0.100 0 d 19.800 20.200 1 1 d1 18.300 18.500 1 1 e0.500??0?? e 9.900 10.100 0 0 l 0.500 0.700 0 0 05 05 n40 40 tsop-a d1 e 1 n cp b e a2 a n/2 d die c l a1
m50flw080a, m50flw080b 40/53 part numbering table 33. ordering information scheme devices are shipped from the factory with the memory content bits erased to ?1?. for a list of available options (speed, package, etc.) or for further information on any aspect of this device, please contact the st sales office nearest to you. example: m50flw080 a k 5 t g device type m50 = flash memory for pc bios architecture fl = firmware hub/low pin count interface operating voltage w = v cc = 3.0 to 3.6v device function 080 = 8 mbit (x8), uniform blocks and sectors array matrix a = 2 x 16 x 4kbyte top sectors + 1 x 16 x 4kbyte bottom sectors b = 1 x 16 x 4kbyte top sectors + 2 x 16 x 4kbyte bottom sectors package k = plcc32 nb = tsop32: 8 x 14mm n = tsop40: 10 x 20mm device grade 5 = temperature range ?20 to 85 c. device tested with standard test flow option blank = standard packing t = tape and reel packing plating technology blank = standard snpb plating g = lead-free, rohs compliant, sb 2 o 3 -free and tbba-free
41/53 m50flw080a, m50flw080b appendix a. block and sector address table table 34. m50flw080a block, sector and lock register addresses block size (kbyte) address range block no and type sector size (kbyte) sector no register address 64 ff000h- fffffh 15 (top) 4 47 fbff002 fe000h- fefffh 4 46 fbfe002 fd000h- fdfffh 4 45 fbfd002 fc000h- fcfffh 4 44 fbfc002 fb000h- fbfffh 4 43 fbfb002 fa000h- fafffh 4 42 fbfa002 f9000h- f9fffh 4 41 fbf9002 f8000h- f8fffh 4 40 fbf8002 f7000h- f7fffh 4 39 fbf7002 f6000h- f6fffh 4 38 fbf6002 f5000h- f5fffh 4 37 fbf5002 f4000h- f4fffh 4 36 fbf4002 f3000h- f3fffh 4 35 fbf3002 f2000h- f2fffh 4 34 fbf2002 f1000h- f1fffh 4 33 fbf1002 f0000h- f0fffh 4 32 fbf0002 64 ef000h- effffh 14 (main) 4 31 fbef002 ee000h- eefffh 4 30 fbee002 ed000h- edfffh 4 29 fbed002 ec000h- ecfffh 4 28 fbec002 eb000h- ebfffh 4 27 fbeb002 ea000h- eafffh 4 26 fbea002 e9000h- e9fffh 4 25 fbe9002 e8000h- e8fffh 4 24 fbe8002 e7000h- e7fffh 4 23 fbe7002 e6000h- e6fffh 4 22 fbe6002 e5000h- e5fffh 4 21 fbe5002 e4000h- e4fffh 4 20 fbe4002 e3000h- e3fffh 4 19 fbe3002 e2000h- e2fffh 4 18 fbe2002 e1000h- e1fffh 4 17 fbe1002 e0000h- e0fffh 4 16 fbe0002 block size (kbyte) address range block no and type sector size (kbyte) sector no register address
m50flw080a, m50flw080b 42/53 note: in lpc mode, a most significant nibble, f, must be added to the memory address. for all registers, a22=0, and the re- maining address bits should be set according to the rules shown in the addr field of table 6. to table 9. . 64 d0000h- dffffh 13 (main) fbd0002 64 c0000h- cffffh 12 (main) fbc0002 64 b0000h- bffffh 11 (main) fbb0002 64 a0000h- affffh 10 (main) fba0002 64 90000h- 9ffffh 9 (main) fb90002 64 80000h- 8ffffh 8 (main) fb80002 64 70000h- 7ffffh 7 (main) fb70002 64 60000h- 6ffffh 6 (main) fb60002 64 50000h- 5ffffh 5 (main) fb50002 64 40000h- 4ffffh 4 (main) fb40002 64 30000h- 3ffffh 3 (main) fb30002 64 20000h- 2ffffh 2 (main) fb20002 64 10000h- 1ffffh 1 (main) fb10002 block size (kbyte) address range block no and type sector size (kbyte) sector no register address 64 0f000h- 0ffffh 0 (main) 4 15 fb0f002 0e000h- 0efffh 4 14 fb0e002 0d000h- 0dfffh 4 13 fb0d002 0c000h- 0cfffh 4 12 fb0c002 0b000h- 0bfffh 4 11 fb0b002 0a000h- 0afffh 4 10 fb0a002 09000h- 09fffh 4 9 fb09002 08000h- 08fffh 4 8 fb08002 07000h- 07fffh 4 7 fb07002 06000h- 06fffh 4 6 fb06002 05000h- 05fffh 4 5 fb05002 04000h- 04fffh 4 4 fb04002 03000h- 03fffh 4 3 fb03002 02000h- 02fffh 4 2 fb02002 01000h- 01fffh 4 1 fb01002 00000h- 00fffh 4 0 fb00002 block size (kbyte) address range block no and type sector size (kbyte) sector no register address
43/53 m50flw080a, m50flw080b table 35. m50flw080b block, sector and lock register addresses block size (kbyte) address range block no and type sector size (kbyte) sector no register address 64 ff000h- fffffh 15 (top) 4 47 fbff002 fe000h- fefffh 4 46 fbfe002 fd000h- fdfffh 4 45 fbfd002 fc000h- fcfffh 4 44 fbfc002 fb000h- fbfffh 4 43 fbfb002 fa000h- fafffh 4 42 fbfa002 f9000h- f9fffh 4 41 fbf9002 f8000h- f8fffh 4 40 fbf8002 f7000h- f7fffh 4 39 fbf7002 f6000h- f6fffh 4 38 fbf6002 f5000h- f5fffh 4 37 fbf5002 f4000h- f4fffh 4 36 fbf4002 f3000h- f3fffh 4 35 fbf3002 f2000h- f2fffh 4 34 fbf2002 f1000h- f1fffh 4 33 fbf1002 f0000h- f0fffh 4 32 fbf0002 64 e0000h- effffh 14 (main) fbe0002 64 d0000h- dffffh 13 (main) fbd0002 64 c0000h- cffffh 12 (main) fbc0002 64 b0000h- bffffh 11 (main) fbb0002 64 a0000h- affffh 10 (main) fba0002 64 90000h- 9ffffh 9 (main) fb90002 64 80000h- 8ffffh 8 (main) fb80002 64 70000h- 7ffffh 7 (main) fb70002 64 60000h- 6ffffh 6 (main) fb60002 64 50000h- 5ffffh 5 (main) fb50002 64 40000h- 4ffffh 4 (main) fb40002 64 30000h- 3ffffh 3 (main) fb30002 64 20000h- 2ffffh 2 (main) fb20002 block size (kbyte) address range block no and type sector size (kbyte) sector no register address
m50flw080a, m50flw080b 44/53 note: in lpc mode, a most significant nibble, f, must be added to the memory address. for all registers, a22=0, and the re- maining address bits should be set according to the rules shown in the addr field of table 6. to table 9. . 64 1f000h- 1ffffh 1 (main) 4 31 fb1f002 1e000h- 1efffh 4 30 fb1e002 1d000h- 1dfffh 4 29 fb1d002 1c000h- 1cfffh 4 28 fb1c002 1b000h- 1bfffh 4 27 fb1b002 1a000h- 1afffh 4 26 fb1a002 19000h- 19fffh 4 25 fb19002 18000h- 18fffh 4 24 fb18002 17000h- 17fffh 4 23 fb17002 16000h- 16fffh 4 22 fb16002 15000h- 15fffh 4 21 fb15002 14000h- 14fffh 4 20 fb14002 13000h- 13fffh 4 19 fb13002 12000h- 12fffh 4 18 fb12002 11000h- 11fffh 4 17 fb11002 10000h- 10fffh 4 16 fb10002 block size (kbyte) address range block no and type sector size (kbyte) sector no register address 64 0f000h- 0ffffh 0 (main) 4 15 fb0f002 0e000h- 0efffh 4 14 fb0e002 0d000h- 0dfffh 4 13 fb0d002 0c000h- 0cfffh 4 12 fb0c002 0b000h- 0bfffh 4 11 fb0b002 0a000h- 0afffh 4 10 fb0a002 09000h- 09fffh 4 9 fb09002 08000h- 08fffh 4 8 fb08002 07000h- 07fffh 4 7 fb07002 06000h- 06fffh 4 6 fb06002 05000h- 05fffh 4 5 fb05002 04000h- 04fffh 4 4 fb04002 03000h- 03fffh 4 3 fb03002 02000h- 02fffh 4 2 fb02002 01000h- 01fffh 4 1 fb01002 00000h- 00fffh 4 0 fb00002 block size (kbyte) address range block no and type sector size (kbyte) sector no register address
45/53 m50flw080a, m50flw080b appendix b. flowcharts and pseudo codes figure 22. program flowchart and pseudo code note: 1. a status check of sr1 (protected block/sector), sr3 (v pp invalid) and sr4 (program error) can be made after each program op- eration by following the correct command sequence. 2. if an error is found, the status register must be cleared before further program/erase controller operations. write 40h or 10h ai09092 start write address and data read status register yes no sr7 = 1 yes no sr3 = 0 no sr4 = 0 v pp invalid error (1, 2) program error (1, 2) program command: ? write 40h or 10h ? write address and data (memory enters read status state after the program command) do: ? read status register ? if sr7=0 and a program/erase suspend command has been executed ? sr7 is set to 1 ? enter suspend program loop if sr3 = 1, ? enter the "v pp invalid" error handler if sr4 = 1, ? enter the "program error" error handler yes end yes no sr1 = 0 program to protected block/sector error (1, 2) if sr1 = 1, ? enter the "program to protected block/sector" error handler suspend suspend loop no yes fwh/lpc interface only
m50flw080a, m50flw080b 46/53 figure 23. double/quadruple byte program flowchart and pseudo code (fwh mode only) note: 1. a status check of sr3 (v pp invalid) and sr4 (program error) can be made after each program operation by following the correct command sequence. 2. if an error is found, the status register must be cleared before further program/erase operations. 3. a0 and/or a1 are treated as don?t care (a0 for double byte program and a1-a0 for quadruple byte program). for double byte program: starting at the start address, the first data byte is programmed at the even address, and the second a t the odd address. for quadruple byte program: starting at the start address, the fi rst data byte is programmed at the address that has a1-a0 at 0 0, the second at the address that has a1-a0 at 01, the third at the address that has a1-a0 at 10, and the fourth at the address th at has a1-a0 at 11. ai09093 read status register yes no sr7 = 1 yes no sr3 = 0 no sr4 = 0 v pp invalid error (1, 2) program error (1, 2) double/quadruple byte program command: ? write 40h or 10h ? write start address and 2/4 data bytes (3) (memory enters read status state after the double/quadruple byte program command) do: ? read status register ? if sr7=0 and a program/erase suspend command has been executed ? sr7 is set to 1 ? enter suspend program loop if sr3 = 1, v pp invalid error: ? error handler if sr4 = 1, program error: ? error handler suspend suspend loop no yes write 40h or 10h start write start address and 2/4 data bytes (3) yes end yes no sr1 = 0 program to protected block/sector error (1, 2) if sr1 = 1, program to protected block/sector error: ? error handler
47/53 m50flw080a, m50flw080b figure 24. quadruple byte program flowchart and pseudo code (a/a mux interface only) note: 1. a status check of sr3 (v pp invalid) and sr4 (program error) can be made after each program operation by following the correct command sequence. 2. if an error is found, the status register must be cleared before further program/erase controller operations. 3. address1, address 2, address 3 and address 4 must be consec utive addresses differing only for address bits a0 and a1. ai09099 write address 4 & data 4 (3) read status register yes no sr7 = 1 yes no sr3 = 0 no sr4 = 0 v pp invalid error (1, 2) program error (1, 2) quadruple byte program command: ? write 30h ? write address 1 & data 1 (3) ? write address 2 & data 2 (3) ? write address 3 & data 3 (3) ? write address 4 & data 4 (3) (memory enters read status state after the quadruple byte program command) do: ? read status register ? if sr7=0 and a program/erase suspend command has been executed ? sr7 is set to 1 ? enter suspend program loop if sr3 = 1, v pp invalid error: ? error handler if sr4 = 1, program error: ? error handler end yes suspend suspend loop no yes write 30h start write address 1 & data 1 (3) write address 2 & data 2 (3) write address 3 & data 3 (3)
m50flw080a, m50flw080b 48/53 figure 25. program suspend and resume flowchart and pseudo code note: 1. if an error is found, the status register must be cleared before further program/erase operations. 2. any address within the bank can equally be used. write 70h ai08426b read status register yes no sr7 = 1 yes no sr2 = 1 program continues write a read command program/erase suspend command: ? write b0h ? write 70h do: ? read status register while sr7 = 0 if sr2 = 0 program completed write d0h program/erase resume command: ? write d0h to resume the program ? if the program operation completed then this is not necessary. the device returns to read as normal (as if the program/erase suspend was not issued). read data from another address start write b0h program complete write ffh read data
49/53 m50flw080a, m50flw080b figure 26. chip erase flowchart and pseudo code (a/a mux interface only) note: 1. if an error is found, the status register must be cleared before further program/erase controller operations. write 80h ai08428b start write 10h read status register yes no sr7 = 1 yes no sr3 = 0 no sr4, sr5 = 0 v pp invalid error (1) command sequence error (1) chip erase command: ? write 80h ? write 10h (memory enters read status register after the chip erase command) do: ? read status register while sr7 = 0 if sr3 = 1, v pp invalid error: ? error handler if sr4, sr5 = 1, command sequence error: ? error handler yes no sr5 = 0 erase error (1) if sr5 = 1, erase error: ? error handler end yes
m50flw080a, m50flw080b 50/53 figure 27. sector/block erase flowchart and pseudo code note: 1. if the block erase command is used on a block that is split into 4kbyte sectors, each of the 16 sectors of the block sho uld be un- locked before performing the erase operation. 2. if an error is found, the status register must be cleared before further program/erase controller operations. write 20h/32h ai09094 start write block/sector address and d0h read status register yes no sr7 = 1 yes no sr3 = 0 no sr4, sr5 = 0 v pp invalid error (1) command sequence error (1) block/sector erase command: ? write 20h/32h ? write block/sector address and d0h (memory enters read status register after the block/sector erase command) do: ? read status register ? if sr7=0 and a program/erase suspend command has been executed ? sr7 is set to 1 ? enter suspend program loop if sr3 = 1, ? enter the "v pp invalid" error handler if sr4, sr5 = 1, ? enter the "command sequence"error handler yes no sr5 = 0 erase error (1) yes no suspend suspend loop if sr5 = 1, ? enter the "erase error" error handler end yes no sr1 = 0 erase to protected block/sector error (1) if sr1 = 1, ? enter the "erase to protected block/sector" error handler yes fwh/lpc interface only
51/53 m50flw080a, m50flw080b figure 28. erase suspend and resume flowchart and pseudo code write 70h ai08429b read status register yes no sr7 = 1 yes no sr6 = 1 erase continues program/erase suspend command: ? write b0h ? write 70h do: ? read status register while sr7 = 0 if sr6 = 0, erase completed write d0h read data from another block/sector or program start write b0h erase complete write ffh read data program/erase resume command: ? write d0h to resume erase ? if the erase operation completed then this is not necessary. the device returns to read as normal (as if the program/erase suspend was not issued).
m50flw080a, m50flw080b 52/53 revision history table 36. document revision history date version revision details 02-feb-2004 0.1 first issue 21-apr-2004 0.2 tsop32 package added 24-may-2004 1.0 first public release 18-aug-2004 2.0 pins 2 and 5 of the tsop32 connections illustration corrected 21-jun-2005 3.0 datasheet status changed to full datasheet.
53/53 m50flw080a, m50flw080b information furnished is believed to be accurate and reliable. however, stmicroelectronics assumes no responsibility for the co nsequences of use of such information nor for any infringement of patents or other rights of third parties which may result from its use. no license is granted by implication or otherwise under any patent or patent rights of stmicroelectronics. specifications mentioned in this publicati on are subject to change without notice. this publication supersedes and replac es all information previously supplied. stmicroelectronics prod ucts are not authorized for use as critical components in life support devices or systems without express written approval of stmicroelectro nics. the st logo is a registered trademark of stmicroelectronics. all other names are the property of their respective owners ? 2005 stmicroelectronics - all rights reserved stmicroelectronics group of companies australia - belgium - brazil - canada - china - czech republic - finland - france - germany - hong kong - india - israel - ital y - japan - malaysia - malta - morocco - singapore - spain - sweden - switzerland - united kingdom - united states of america www.st.com

▲Up To Search▲

Price & Availability of M50FLW080AK5T

	To Download M50FLW080AK5T Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .